Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
2 out of 3 committers have signed the CLA.

✅ gnv-zeeve
✅ radhe-zeeve
❌ arjunzeeve
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

The applicant has requested the discussion of the application to happen in a private chat room.

One minor thing: Could @arjunzeeve still sign the terms and conditions?

Seems like this isn't working, details shared on private chat.

One minor thing: Could @arjunzeeve still sign the terms and conditions?

It seems to have stuck, we did try it multiple times as well as using different browsers. Shared screenshots on private chat. Please suggest a way out.

I looked into it, and I believe it's okay. We had this issue before, and it happened because of a spelling issue that does seem to cause problems with the bot.arjun-zeeve has successfully signed the terms. See below:

Congratulations and welcome to the Web3 Foundation Grants Program! Please refer to our Milestone Delivery repository for instructions on how to submit milestones and invoices, our FAQ for frequently asked questions and the support section of our README for more ways to find answers to your questions.

Before you start, take a moment to read through our announcement guidelines for all communications related to the grant or make them known to the right person in your organisation. In particular, please don't announce the grant publicly before at least the first milestone of your project has been approved. At that point or shortly before, you can get in touch with us at [email protected] and we'll be happy to collaborate on an announcement about the work you’re doing.

Lastly, please remember to let us know in case you run into any delays or deviate from the deliverables in your application. You can either leave a comment here or directly request to amend your application via PR. We wish you luck with your project! 🚀

@radhe-zeeve It seems the current ink-playgroud.substrate.io is down. Some details in:

• https://ink-playground.substrate.io/ is 404 use-ink/ink-playground#704
• https://forum.polkadot.network/t/ink-playground/3052/3

Do you use kubernetes when working on the playground?

@JoshOrndorff we are aware ink-playgroud.substrate.io is down. As mentioned in the issue Polkadot team is trying to migrate to pure k8 based deployment, as for the current development we are using docker, if anything changes in deployment process we would pivot and make adjustments to our development to accommodate the new deployment process.

Hi @radhe-zeeve just left a comment in the private channel, FYI.

Hi @radhe-zeeve how is the milestone coming along?

@keeganquigley We have already created PR for one of the issue and marked it ready for review recently Add new Ink Version update support by radhe-zeeve · Pull Request #815 · paritytech/ink-playground, resolution for other two issues required for the first milestone is being worked on and will be presented in few days.

Thanks @radhe-zeeve feel free to provide an update in the private Element chat.

I will be delivering an final updated code within the next couple of days.

Hi @radhe-zeeve still planning on delivering this?

@keeganquigley already opened the PR last week and pinged cmichi on the PR, no response yet

PR's: use-ink/ink-playground#817, use-ink/ink-playground#815

Thanks for the update @radhe-zeeve yes unfortunately it will probably be a while since they are swamped. In the meantime, in order to get paid for this milestone we would need you to submit a delivery PR in the repo: https://github.com/w3f/Grant-Milestone-Delivery

Its okay if the PRs are still open, but that way you can document what work was done. Are you able to complete this? Thanks!

@keeganquigley Sure, will open a PR with documentation on https://github.com/w3f/Grant-Milestone-Delivery.

pinging @radhe-zeeve

Hey @semuelle let us know in case you still have some open items on this and we can quickly close them.

cc: @radhe-zeeve

Thanks, @gnv-zeeve. We have a bit of a backlog at the moment, so it will probably take a few more days. I'll share feedback on the pull requests.